home *** CD-ROM | disk | FTP | other *** search
-
- HOW TO SEND BUG REPORTS FOR MKICK
- ---------------------------------
-
- If MKick doesn't work on your machine and you think it should work, send
- me a bug report (to <mjsoft@k332.feld.cvut.cz>). Each bug report should
- contain:
-
- (1) Exact description of what's going wrong (reports containing only 'MKick
- doesn't work on my machine' are totally useless).
-
- (2) Which Kickstart version you're trying to use, including the machine it's
- built for (there exist A600, A1200 A3000 and A4000 version of most
- Kickstarts).
-
- (3) What's the effect of NOTAGS and NOTEST options. Also, if you suspect MKick
- to have some problems with your memory configuration, try to force
- each of your memory types by CHIP, FAST, EXT and NAC options.
-
- (4) What colors appear on the screen if the DEBUG switch is turned on. (They
- have been selected to be different enough even on mono monitors.)
-
- (5) Output of some system configuration analyser (best is CBM's ShowConfig with
- the DEBUG switch turned on -- it's included on WB3.1 disks, also possible
- to use some SysInfo utility).
-
- (6) Name of Kickstart header file you're using (if you made some changes to it,
- send the changes). If you've generated the KSHD from SKick RTB/PAT files,
- specify names of these files and version of SKick archive you've taken them
- from.
-
- (7) Complete description of your hardware configuration. (Especially various
- hardware hacks, accelerator boards etc.)
-
- (8) If MKick starts the Kickstart and no expansion boards (fast memory, hard
- drives and similar devices) are visible or if the Kickstart doesn't survive
- reset, include output of the KickStat utility (also included in this
- archive).
-
- (9) Output of the KickInfo utility if applied to your Kickstart (included in
- this archive).
-
- (10) Version of MKick (you can obtain it by typing MKick ?, then answering ? at
- the prompt).
-
-
- Thanks
-
- Martin
-